● {{ m.diet }}{{ m.spice }} spice
{{ m.name }}
{{ m.ingredients }}
{{ m.priceL }}{{ m.stockL }}
Today’s run of show
{{ p.eventType }}{{ r.time }}{{ r.label }}{{ r.state }}
NO. 01 · SETUP
Configure a Table once, reuse it daily.
Admins define budget, restaurants, timing, visibility and reminder rules. Any employee can create a Table; org policy controls what can be ordered.
STEP 1
{{ cfgA.mark }}The Table
What it is and how people choose.
STEP 2
{{ cfgB.mark }}Budget & plan
Limits employees see, and what the company covers.
STEP 3
{{ cfgC.mark }}Timing & delivery
When choices close, where food lands, how people hear.
Reminder channels
{{ r.k }}{{ r.v }}
{{ cfgSummary }}
MY PLATE · CUTOFF {{ p.cutoff }}
Your lunch, {{ emp }}.
Confirm before {{ p.cutoff }}. If you don’t, your default order is used.
{{ l.name }}{{ l.restaurant }} · {{ l.priceL }}{{ l.qty }}
Your plate is empty.
MY REQUESTS
Out-of-policy asks.
Your team lead reviews these before the cutoff.
No requests. Everything you picked is within policy.
NO. 03 · OFFICE CART
One cart, controlled by policy.
Employee choices roll up by restaurant and delivery wave. Lock the menu, clear approvals and place one order.
People completed{{ doneLabel }}{{ completion }}% response
Budget used{{ totalL }}{{ remainingL }} remaining
Approval queue{{ pendingApprovals }}Team lead, then admin
Delivery plan{{ waves }}Grouped by ETA
{{ g.restaurant }}{{ g.wave }}
{{ i.employee }}{{ i.name }}{{ i.priceL }}{{ i.qty }}
The tray is empty
NO. 02 · FINALISE & BILL
{{ subL }}
{{ fzTitle }}
{{ fzSub }}
{{ g.restaurant }}{{ g.wave }}
{{ i.employee }}{{ i.qty }} × {{ i.name }}{{ i.priceL }}
No meals yet. The team lead hasn’t submitted an order.
PERSONBUDGETCHOICEAMOUNTSTATUS
{{ e.name }}{{ e.role }} · {{ e.level }}₹{{ e.budget }}{{ e.choice }}{{ e.amtL }}{{ e.status }}
{{ i.kind }}{{ i.title }}{{ i.detail }}
✓
No blocking issues on this order.
{{ m.name }}{{ m.role }} · {{ m.level }} · ₹{{ m.budget }} budget
{{ m.tag }}DEFAULT
LAST THREE ORDERS
If {{ m.name }} doesn’t reply by {{ p.cutoff }}:
Everyone has chosen or opted out.
Schedule & billing
NO. 05 · APPROVALS
Anything outside policy, in one queue.
Team leads approve first; org admins handle escalations, subscriptions and payment policy.
NO. 06 · INSIGHTS
Is this worth a regular habit?
Repeat orders, plan fit and organiser time saved show whether the demand lasts.
Recurring orders18Last 30 days
Organiser time saved42 minPer meal cycle
Reminder actions64%Acted on, not dismissed
Plan signal{{ p.subscription }}Likely fit
Product health
{{ h.label }}{{ h.v }}
Experiments to run
{{ t.k }}{{ t.v }}